home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir34
/
ddupe210.zip
/
DDUPE_HM.TXT
< prev
next >
Wrap
Text File
|
1994-07-02
|
37KB
|
716 lines
#1#
DOSDupe
by MaeDae Enterprises
DOSDupe turns your computer into a high speed disk duplicating machine
equalling the performance of many dedicated hardware diskette duplicators
costing thousands of dollars. Comments or suggestions for improving
DOSDupe will be appreciated.
DOSDupe requires an IBM PC or compatible with 256K of RAM. Display
adapters known to work with DOSDupe are the IBM monochrome (MDA),
color (CGA), enhanced graphics (EGA), and video graphics array (VGA)
adapters.
DOSDupe supports all common 5¼" and 3½" formats.
#20#
General help for all menus:
This menu is broken up into two basic windows. The window at the top
of your screen shows several options to choose from. The window at the
bottom of the screen expands on what will occur if you choose the
highlighted option (the one that has a different background color).
Options may be selected in one of two ways. You can either press the
first letter of the desired command or move the highlight bar over the
desired option and press enter. To move the highlight bar use either
the space bar, up arrow, down arrow, left arrow, or right arrow. You can
also use home to move to the first top line item on the menu.
Using the first letter of a command only works in the ACTIVE window. If
you don't have any pulldown then the active window is the top window.
Once you pulldown one of the options that becomes the active window. You
must use one of the commands in the pulldown once it is active. You can
always use Escape to back out of the pulldown and return to the top menu.
#21#
You are now using the DOSDupe Main Menu. From here you can access the main
functional areas of DOSDupe. Refer to the On-Line Manual to get a feel
for what a fully featured diskette duplicator can do.
An additional status window is displayed near the bottom of your screen.
It shows you the status for load, copy, compare, and format. A time in
seconds is displayed after each type of operation. This shows you the
time it took for the previous load, copy, etc. If 0 seconds is displayed,
then you haven't performed an operation to allow DOSDupe to time that
function. DOSDupe uses a "smart" form of counting where the copy and
compare counters are reset to zero when you load a disk. That way they
always provide you information relative to the disk you are working with.
Please note that an abbreviated directory window will appear in the middle
right of your screen as soon as a valid source diskette has been loaded.
It will show the diskette volume label (if any) and first four file names.
We have tried to design DOSDupe to let you get your job done quickly
and easily. Please feel free to forward any suggestions for improvement
to us at MaeDae Enterprises, Attn: DOSDupe Author.
#90#
DOSDupe couldn't locate your path. Are you sure you entered the correct
path to get to your file. Computers are dumb, you have to tell them
everything.
#100#
Drive was not ready for read/write. Please ensure you have a floppy in
the drive and the drive door is closed.
Sometimes on very fast AT compatible computers with 1.2 Mb diskette drives
the drive can't respond quickly enough. In this case try the operation
again or add a utility to modify the timeout on the drive. Several
programs are available to fix this disk drive timeout problem.
#200#
Help for Directory Screen: To use the file use the up or down arrows on
the numeric keypad to highlight a file name and then press enter.
All files in the directory listing are sorted. DOSDupe can handle a
directory containing up to 500 files. If you have more files than that
in a SINGLE directory then please break the directory into smaller ones
before running DOSDupe.
Cursor key movements:
Up Arrow - Move up one file. Down Arrow - Move down one file.
PgUp - Move up one page of files. PgDn - Move down one page of files.
Ctrl+Home - Move to the first file in the directory.
Ctrl+End - Move to the last file in the directory.
Use Enter to select the highlighted FDF file and start operations.
#201#
General note:
The file sizes are shown in K bytes to conserve screen space. This
abbreviated display method allows additional information to be shown
on the directory screen. Each K is actually 1024 bytes. If you use a
DOS directory listing to show the size of a file, it will show a 100K
file as 102,400 bytes (100 times 1024).
#250#
An error was detected while trying to read your source diskette. Please
ensure the diskette is inserted in the specified drive and that the drive
door is closed. Also you might try to take the diskette out and re-insert
it back into the drive. Sometimes the diskette isn't centered correctly
within the disk drive.
The source was not loaded so you will not be able to make any copies.
All standard 160K, 180K, 320K, 360K and 1.2M 5¼" and 720K/1.44M 3½"
diskette formats are supported.
#300#
DOSDupe could not perform the requested operation. This screen gives help
related to the format and copy diskette operations. An error occured
during the requested operation. Listed below are some helpful hints
with a detailed error listing provided on the next screen.
Please ensure: 1. The diskette isn't write protected.
2. There really is a diskette in the destination drive.
3. There is no obvious physical damage to the diskette.
4. You aren't trying to save to a 1.2 Mb diskette in a
360 Kb disk drive or a 1.44M diskette as a 720K disk.
5. You don't have any disk cache software that is trying
to buffer writes to your floppy drive.
6. You really do have the specified destination drive.
This error may be generated on some hard disk based systems where you boot
from the hard disk. Try booting from a floppy containing your DOS. The
problem may go away. We have seen this happen with certain versions of
DOS, specifically Compaq DOS 3.31 and IBM PC DOS 4.0. We will continue to
research the problem and provide an update ASAP!
The next help screen will provide a detailed explanation of the error
codes.
#301#
Error codes:
Code Description
════ ═══════════════════════════════════════════════════════════════
0 Unable to bring the diskette in drive up to speed for operation
1 Bad command: invalid request made to diskette controller
2 Bad address mark: sector ID marking invalid or not found
3 Write protect error: attempt to write on protected diskette
4 Bad sector: requested sector not on diskette
8 DMA failure
9 DMA boundary error: attempt to DMA outside 64K area
16 Bad CRC: diskette read found invalid parity check of data
32 Controller failed: diskette controller malfunction
64 Bad seek: move to requested track failed
128 Time out: drive did not respond
Note: The description of these error codes were obtained from several
sources for the IBM PC. The descriptions are very generic because there
can be a wide variety of problems return the same error code. We don't
mean to be cryptic but there is really no way to return a specific error
code for every possible error condition.
#400#
This screen shows you a lot of technical information that probably seems
very confusing at first. DOS uses all this information and more to keep
track of information stored on floppy diskettes.
As the IBM PC and DOS has evolved over the last few years so has the
formats of the media used in the computer. This has caused a large number
of formats for the media. DOSDupe uses the following drive types:
0 160K Single sided, 40 track, 8 sectors per track
1 180K Single sided, 40 track, 9 sectors per track
2 320K Double sided, 40 track, 8 sectors per track
3 360K Double sided, 40 track, 9 sectors per track
4 720K Double sided, 80 track, 9 sectors per track
5 1.2M Double sided, 80 track, 15 sectors per track
6 1.44M Double sided, 80 track, 18 sectors per track
Other information displayed on this page will need to be looked up in a
DOS technical reference manual. You can easily obtain a book containing
this information from your local computer store.
#401#
A map of your diskette is also laid out before you. Any cluster with a *
contains information. Any cluster with a . doesn't contain information.
Information on how the clusters relate to absolute sides, tracks, sectors,
etc. can be obtained using the info/drive status option under the utility
section of DOSDupe.
#500#
DOSDupe uses a 16 bit CRC to determine when damage has occured on a Floppy
Disk File (FDF). Our extensive built-in testing has determined that this
diskette (stored as file) is damaged. DOSDupe will not allow you to use a
damaged floppy disk file!
We check check all FDFs using a 16 bit CRC. This will catch modifications
to the data for about 99.996% of the cases. Using a 16 bit CRC check is
much more reliable than a faster checksum while adding only one to two
percent speed overhead! Our high speed assembly language CRC allows us to
completely protect your data without slowing you down.
Also, we have added ultra high speed assembly language data compression
for your FDF files. The data compression/expansion is so fast that it
will almost always load and save faster than an uncompressed .FDF file.
Because of this, we no longer support the older non-compressed formats.
We hope you appreciate the extra measure of safety we have added here.
#700#
You must first load a diskette before you can perform operations using it.
Use the load disk option to load a diskette.
Did you have a disk error on the previous read? Only diskettes which have
been read into memory can be written back out.
If you are using this option to format diskettes first format a clean
master diskette using your DOS. Load that diskette into DOSDupe. Turn the
forced format option on for best results. You can now save as many copies
of the diskette as desired. The result is the same as using DOS's format
command but is faster.
#750#
You must first load a diskette before you can do a directory of it. Use
the load disk option to load a diskette.
The in-memory directory command looks at the diskette image stored in RAM
and generates a directory from it instead of re-reading the diskette. This
is much faster and more convient for the user.
#760#
The in-memory directory command allows you to do a directory of the source
disk you have loaded in memory. This allows you to quickly check the
contents of the in-memory diskette to ensure you have the correct diskette
loaded for copies or compares.
The in-memory directory displays a file number to keep track of the file
you are on, the filename, file extension, and file size in bytes. This
directory is obtained by checking the file allocation table (FAT) which is
located in the image of the diskette stored in memory. This technique
doesn't use DOS. DOSDupe tries to obtain filenames from the information
stored in memory. There is no other way without asking DOS to read the
diskette directory from the floppy diskette. Our technique works on all
versions of DOS up to DOS 4.01. Since this is the latest version available
at this time, we feel the technique works under all known conditions.
However, future versions of DOS may change the format of the FAT stored on
floppy diskettes. If this occurs, contact us to upgrade to the latest
version of DOSDupe that supports your new DOS version.
#800#
Use of this option is highly recommended for companies producing
diskettes which need to be read on the widest range of computers. By
forcing the format of a diskette you guarantee that data is laid down
cleanly on the new tracks. If you simply write over old data without
reformatting the diskette it can cause some problems with 1.2 Mb floppy
drives. The 1.2 Mb drives are very picky on the AT. By reformatting the
floppy it helps readability.
Use of the forced format option will cause the copy operation to take
about 50% longer than saving to a formatted floppy without forced format.
If you are constantly saving to blank unformatted diskettes it is
strongly recommended that you set the default at forced format. Without
forced format DOSDupe first tries to write to the diskette, if that fails
it will then set forced format to on for this one copy only. You can
save the one or two seconds test time by telling DOSDupe to just go ahead
and format the floppy without testing to see if the diskette is already
formatted.
Note: If you are always working with unformatted diskettes, using this
option will save you about 1/2 second per copy. DOSDupe, like DOS, first
tries to write to the floppy before resorting to formatting. You are
saving the time it takes to determine the floppy isn't formatted.
#850#
Use of this option is highly recommended for companies which reuse high
quality previously formatted defect free diskettes. Since the entire
diskette surface isn't checked, this option could create problems for
questionable diskettes. We recommend its use only on defect free high
quality diskettes! Never under any condition use this option if the
diskette hasn't been previously formatted!
Now the good news. A diskette can be re-formatted in as little as two
seconds using this option!
If the diskette hasn't been previously formatted, DON'T use this option!!
As an extra protection, we have added a check to ensure you don't quick
format only the first track of an unformatted diskette. We check the
second diskette track and then default to formatting the entire diskette
if the second track can't be read.
#900#
This option allows you to define the default path for accessing the
on-line manual and context sensitive help. Make sure you include the
index file (.INX) along with the help/manual file (.TXT) in the specified
directory.
#1000#
This option allows you to enable/disable the sound or beeps on errors.
Some people find programs that beep on errors to be annoying (me for
one). This option will allow you to disable ALL warning beeps in
DOSDupe.
#1010#
This options allows you to limit use of XMS and EMS memory by DOSDupe.
DOSDupe normally uses regular RAM, XMS, EMS, and then virtual memory (a
disk file) as the default. This option allows you to bypass the normal
operation and limit memory usage to only RAM and virtual memory.
When would you want to exclude XMS and EMS? Sometimes network drivers
don't work well with software that tries to maximize the use of your total
memory. We have provided the option to disable use of XMS and EMS if this
is a problem with your system.
#1100#
This menu allows you to change all the colors used in DOSDupe. To change
a default color - first use the up or down arrow key to select the color,
then type in the new color. When you have changed all the colors press
Ctrl+D to display these colors in a sample window. As with all
installation options, these changes will not be used until you choose the
retain option on the main menu. This allows you to experiment with the
installation options and then not have to lose your original defaults.
Please keep in mind the foreground text colors can be 0-15, the
background 0-7. If you choose a text color the same as a background color
then the text will disappear. You may notice some of your installed color
combinations result in invisible lines on the Ctrl+D popup window.
Please be careful not to choose this color for one of your text colors!!
Note: For many of the DOSDupe installable options and user inputs you
will see a prompt containing the characters . If you count the
number of 's you will find the maximum number of characters that can be
entered. ESC is used throughout DOSDupe to signal "I want out". Press
Enter, up arrow, down arrow, or whatever is asked for to enter the desired
value. Escape will throw away any immediate changes and get you out
of the area you are in.
#1101#
Please note that the background color (0-7) is one digit long and the
foreground color (0-15) is two digits long. That is why you will see the
input prompt (the s) change it's width as you go between the colors.
#1200#
This screen shows the possible combinations of colors in DOSDupe.
If you are using a non IBM display adapter you may have to "play" with the
colors to get a pleasing combination. DOSDupe defaults to colors that work
well with the IBM Color Graphics Adapter, IBM Enhanced Graphics Adapter,
and IBM Monochrome Display Adapter.
On some monochrome display adapter clones you may need to alter a
foreground text color to get the background to change intensity.
The default combination of colors will work on any 100% IBM PC compatible
display adapter!
#1300#
DOSDupe allows the help & manual paths, program colors, etc. to be saved
in a configuration file. If no configuration file is specified on the
command line (ex. C:>DOSDupe /C=C:\DOSDUPE\MyConfg.CNF) when you call
up DOSDupe then DOSDupe will use the default name of DOSDUPE.CNF.
You are being asked for the name of the configuration file to load. You
may have several configuration files saved under different names.
Example: BW.CNF (for black and white composite monitors attached to a
composite color card), etc.
Please make sure that the configuration file you are asking DOSDupe to use
is really an DOSDupe configuration file!
Remember you can always press ESC if you got into this area by accident.
#1400#
DOSDupe allows the default help/manual paths, program colors, etc to be
saved in a configuration file. If no configuration file is specified on
the command line (ex. C:>DOSDupe /C=C:\DOSDUPE\MyConfg.CNF) when you call
up DOSDupe then DOSDupe will use the default name of DOSDUPE.CNF.
You are being asked for the name of the configuration file to save all the
program defaults to. You may have several configuration files saved under
different names.
Examples: BW.CNF (for black and white composite monitors attached to a
composite color card), etc.
Please remember you can always press ESC if you got into this area by
accident.
#1500#
The diskettes you are trying to compare are not the same type. Diskettes
come in several different capacities. You are trying to compare one
format with another. This can't be performed.
Use the utilities section of DOSDupe to determine the diskette type.
#1510#
The compare of the two diskettes failed. The diskette stored in memory is
not the same as the diskette you asked DOSDupe to compare it to.
#1520#
The diskette in memory is the same as the diskette you compared it to.
Both the format and the contents are the same.
A complete byte for byte comparison was performed. The comparison was
performed on the in-memory disk and the specified diskette one byte at a
time. If any byte wasn't the same, you would have been shown a different
window saying that the diskettes were not the same.
#1600#
This screen allows you to select the default format capacity for your
disk drives. You specify the format for each drive by typing the drive
letter, an equal sign, and then the desired format capacity. Do not use
any spaces within the specification. For example: A=360 is ok, but
A= 360 or A=3 60 are not! You can change the format capacity of any drive
or all drives by simply editing the displayed values. Also, make sure the
drive you specify is a DOS compatible drive. Only those drives normally
addressable through DOS via INT13 (a DOS standard access method) are
supported.
Editing keys: Keypad Home, End, left arrow, right arrow, insert, delete,
and much more.
Each of your floppy drives support a high end format capacity but may also
be able to support older and smaller disk formats. For example: The
first IBM PC back in 1981, only supported the 5¼" 160K format. With the
improvements in disk drive technology and DOS revisions the capacity grew
in steps up to the current 360K for the standard double sided double
density 5¼" drive. We provide support for the older formats, allowing
compatibility with the older machines and users of older versions of DOS.
#1625#
DOSDupe could not understand the format you specified. One of two
possibilities exist. Either you specified the information in an invalid
format or the capacity you specified for one of the drives is not valid.
Assume drive A: is a 720K drive and B: is a 360K drive.
Valid commands: A=720 B=360 or A=720 B=160 or A=720 B=180
Invalid commands: A=360 B=720 or A=720 B=3 60 or A =720 B=360
Do not use any spaces in the drive=capacity statement. Ensure the capacity
you specify is valid and that the drive is a DOS compatible drive.
An arrow is probably shown on your screen under a section of the format
specification. This shows where we were in working with your desired
formats when the error was encountered. Usually the arrow will appear
immediately after the end of the statement that caused the error. For
example: A=160 B=360 As the formats are looked at, the arrow would be
pointing to the space after 160 (it had just finished getting the desired
format capacity). A check would be performed to see if drive A could
support a 160K format (a 720K drive can't). You would then be given the
error message.
#1650#
This screen allows you to define the different drives on your computer and
their maximum capacity. You specify the capacity for each drive by typing
the drive letter, an equal sign, and then the drive capacity. Do not use
any spaces within the specification. For example: A=360 is ok, but
A= 360 or A=3 60 are not! You can change the maximum capacity of any drive
or all drives by simply editing the displayed values. Also, make sure the
drive you specify is a DOS compatible drive. Only those drives normally
addressable through DOS via INT13 (a DOS standard access method) are
supported.
Editing keys: Keypad Home, End, left arrow, right arrow, insert, delete,
and much more.
Many of the older computers don't directly support the newer drives using
the BIOS calls. Because of this, we allow you to override the information
we obtain from BIOS calls. Some of the older computers may report that a
drive may not exist or be the wrong size when we inquire thru BIOS calls.
If your configuration differs from the one shown, add additional drives
and correct capacities. After you save the configuration, DOSDupe will use
your information and ignore the initial drive information provided
by BIOS calls.
#1675#
The only valid capacities in K are 360, 720, 1200, or 1440!
DOSDupe could not understand the capacity you specified. One of two
possibilities exist. Either you specified information in an invalid format
or the capacity you specified for one of the drives is not valid.
Assume drive A: is a 720K drive and B: is a 360K drive.
Valid command: A=720 B=360
Invalid commands: A=360 B=720 or A=720 B=3 60 or A=720 B=320
Do not use any spaces in the drive=capacity statement. Ensure the capacity
you specify is the maximum capacity supported by the drive and that the
drive is a DOS compatible drive.
An arrow is probably shown on your screen under a section of the capacity
specification. This shows where we were in working with your desired
formats when the error was encountered. Usually the arrow will appear
immediately after the end of the statement that caused the error. For
example: A=160 B=360 As the capacities are looked at, the arrow would be
pointing to the space after 160 (it had just finished getting the actual
maximum drive capacity). 160 is an invalid maximum capacity!
#1700#
DOSDupe "spools" your diskette to file on the specified drive when you run
out of normal RAM in your computer's main memory. When working with 3½"
disks, your computer can't store the entire diskette in memory. We send
the portion that can't be stored in main memory to a disk file. This
option allows you to specify which drive will contain the temporary file.
A file by the name of VIRTDISK.$$$ is created in the root of the specified
spool drive and used for the temporary storage of the portion of the
diskette that won't fit into memory. This file is created for spooling
and then erased after you finish using DOSDupe.
Please ensure there is about one megabyte of free disk space available on
the specified drive. Not all of this will be used but it is the suggested
minimum to prevent any possible problems. For higher performance, specify
a large RAM disk as the spool drive. This will allow DOSDupe to spool to
a high speed device, making the copying of larger diskettes very fast.
Specify your extended or expanded memory as a RAM disk and install
DOSDupe to spool to this drive for much faster operation.
Drives A-Z are allowed for spooling. Do NOT spool to the same drive that
you are copying! Using floppy drives for spooling is not recommended.
#1800#
This option allows you to address any floppy drive attached to your
computer as long as it is supported in your computer's Basic Input Output
System (BIOS). Press the letter corresponding to the drive you want to
access (example: G for diskette drive G:). Special checks are performed
to ensure that you don't use a hard disk or similar type drive for this
operation. Most of us don't appreciate it when a program accidentally
reformats our hard disk.
Most computers support drives A: and B: as floppy drives (removable media
drives). Hard disks normally start at C: and run thru Z: (and aren't
normally removable). Some computers are a little different, maybe even a
little strange. They may even have a floppy drive addressed as G:. We have
built in support for floppies addressed as A: thru Z: as long as your
computer fully supports them in its BIOS. We also work with most drives
that use a device driver (in the CONFIG.SYS file) to extend the ROM BIOS.
#1810#
The floppy drive you have selected is not recognized by your system as a
normal floppy drive. We ask your computer using INT13 in your computer's
Basic Input Output System (BIOS) what drives you have. It reported that
the drive you selected is not a floppy drive. Some add-on floppy drives
may provide you with some software that "tricks" your computer into
thinking it has additional drives. This kind of thing normally works
around the BIOS and isn't compatible with normal BIOS calls. We can't
guarantee proper operation with your diskette drives in these cases.
#2000#
DOSDupe ran out of memory while trying to perform the requested operation.
Generally this will only happen if you have limited free system memory
(RAM) and try to perform an operation that requires a lot of memory.
Possible corrective measures:
1. Limit the number of memory resident programs you load.
2. Upgrade your system RAM if you have less than 640K.
3. Provide additional free disk space on the drive you specified for the
spooling of large floppies.
4. Allocate more space to your RAM disk if you have chosen one for higher
performance overflow spooling (virtual memory).
#20050#
Quick startup info:
DOSDupe is a diskette duplication program which lets you, the user,
mass produce diskettes quickly and easily. It allows you to read a
diskette once and then make as many copies as you want. DOSDupe supports
5¼" 160K, 180K, 320K, 360K, and 1.2M; also 3½" 720K and 1.44M.
To copy a diskette use the Load pulldown off the main menu. Insert the
diskette you would like to copy. Next tell DOSDupe where you put
the diskette by selecting the Load pulldown and pressing A for drive A: or
B for drive B:. Your diskette will be loaded into memory. Take out your
master source diskette and place the diskette you would like to make the
copy on into a drive, it doesn't matter which drive. Now it is time to
tell DOSDupe to make the copy. Select the Copy pulldown and press A to
make the copy in drive A: or B for drive B:. DOSDupe will automatically
format your floppy if it isn't already formatted. Repeat this step to
make as many copies as you want. Isn't it nice not to have to reload your
source diskette each time?
DOSDupe now supports command line use. For example: DOSDupe A: A:
F1 is available to call up help while you are using DOSDupe.
#20051#
┌──────────────────────────┐
│ Commonly Asked Questions │
└──────────────────────────┘
1. Will DOSDupe duplicate copy protected diskettes? No. DOSDupe will only
duplicate unprotected diskettes with no bad sectors.
2. How does DOSDupe manage to copy even 1.44M floppies in a single pass?
DOSDupe holds as much of the diskette in memory as possible. The rest
of the diskette is spooled to a file on another drive. Use a RAM drive
to provide maximum performance (lightning fast).
3. Will DOSDupe allow me to save diskettes on my hard disk for later
recall? Yes! DOSDupe will write any diskette to a compressed data file
using data validity checks (CRCs) to allow high speed recall later.
#20100#
DOSDupe allows you to read an entire diskette into memory then make as
many copies as you want without reading the master diskette again. To
do this it must retain an image of the master diskette in memory. This
image can take up to 720K of storage space. The portion of the diskette
that won't fit into memory is spooled to another drive.
DOSDupe out performs DOS's diskcopy both in speed and safety of the
operation. DOSDupe speeds up the access times of your disk drive allowing
quicker reads and writes. It also verifys the copy by checking the CRC
written to the diskette during the copy process.
When making a copy, DOSDupe (unless told otherwise) will check the
diskette to see if it is already formatted and then proceed either with
the copy or the format and copy. Just feed it diskettes, you don't need
to worry about the destination diskette. Nothing could be easier!
System requirements: An IBM PC or totally compatible clone, 256K of RAM,
and IBM PC DOS version 3.0 or later. DOSDupe should
work with any version of MS DOS 3.1 or later but has
not been tested with all the possible MS DOS
versions.
#20200#
╒═══════╦═══════════════════════════╦═══════════════════════════╕
│ PCDOS ║ 360K 5¼" Diskette ║ 1.44M 3½" Diskette │
│ ───── ╟──────┬──────┬──────┬──────╫──────┬──────┬──────┬──────┤
│DOSDupe║ Load │ Save │FmtSav│Format║ Load │ Save │FmtSav│Format│
╞═══════╬══════╪══════╪══════╪══════╬══════╪══════╪══════╪══════╡
│ DOS ║24 sec│41 sec│83 sec│44 sec║60 sec│92 sec│178sec│95 sec│
├───────╫──────┼──────┼──────┼──────╫──────┼──────┼──────┼──────┤
│DOSDupe║18 sec│30 sec│50 sec│40 sec║35 sec│59 sec│95 sec│80 sec│
╘═══════╩══════╧══════╧══════╧══════╩══════╧══════╧══════╧══════╛
Notes: Times may change as we continue to improve DOSDupe. Please note
that the faster your computer, the more DOSDupe out performs IBM
PC DOS. We used normal RAM/XMS overflow memory. We used freshly
formatted diskettes that were approximately 75% full. Less full
diskettes will result in far higher performance!
DOSDupe can make multiple copies/compares per read, most versions
of DOS can't. DOSDupe is faster than PC DOS (2-3x) for multiple
operations because it doesn't reload the source and makes copies
of even 1.44M diskettes in a single pass! We assumed 10 seconds
for several manual swaps of 1.44M 3½" diskettes for loads/saves.
#20201#
All benchmarks are based on version 2.00 of DOSDupe running on an
IBM PS/2 model 70. Run your own timing tests using your hardware, don't
take our word that we are faster. The only true test of how quickly
DOSDupe will perform diskette operations on your hardware is to actually
time them. We invite you to put DOSDupe to the test.
The above times are affected by the DOS version, both by its revision and
its source (IBM, Compaq, etc). Any small change in your hardware may
throw off timing of DOSDupe. Memory resident programs slow down DOSDupe
and may drastically (up to 50%) slow the disk operations. Even such a
small thing as displaying the track number while copying took many hours
of work to speed up to where it didn't slow down operations.
All tests were run with IBM PC DOS with no memory resident programs. If
your timing tests show results radically different from the above figures
please write us. If you did better, we will praise DOSDupe, if you
did worse we will try to find something to blame it on.
Please note that we far out perform DOS on 1.44M 3½" media because of our
ability to work with the diskette in a single pass without requiring you
to swap diskettes. We also use "smart" loading/saving. If your diskettes
aren't almost full, our performance will be even higher!
#20300#
HISTORY OF REVISIONS:
═════════════════════
DOSDupe v1.00 Nov 1987 Released shareware under a different name. It
was updated and released under a different name
until 1994. This powerful program is now
available to you under the name DOSDupe directly
from its author.
DOSDupe v2.10 Jul 1994 Updated and released by author as DOSDupe.
#20500#
GENERAL:
════════
1. DOSDupe was developed by David Black of MaeDae Enterprises.
2. DOSDupe was written in C with the core disk routines and several
other speed critical routines in high speed assembly language. The
source for DOSDupe consists of about 9,000 lines of code.
#END#